Hybrid FDD/TDD wireless network

ABSTRACT

Technologies and implementations for wireless communication in a wireless network including transmitting downlink information on a first frequency channel to Frequency Division Duplexing (FDD) User Equipments (UEs), transmitting downlink information on a second frequency channel during downlink portions of Time Domain Duplex (TDD) frame periods of the second frequency channel to TDD UEs, wherein the second frequency channel is the same as the frequency channel on which the FDD UEs are configured to transmit, and controlling uplink transmissions from the FDD UEs to occur only during uplink portions of TDD frame periods of the second frequency channel.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation application under 35 U.S.C. §120 of U.S. application Ser. No. 15/863,003, filed on Jan. 5, 2018, nowU.S. Pat. No. 10,334,575, which is a continuation application under 35U.S.C. § 120 of U.S. application Ser. No. 14/783,309, filed on Oct. 8,2015, now U.S. Pat. No. 9,867,168, which is a U.S. National Stage filingunder 35 U.S.C. § 371 of International Application No. PCT/US13/38899,filed on Apr. 30, 2013. U.S. application Ser. No. 15/863,003, U.S.application Ser. No. 14/783,309, and International Application No.PCT/US13/38899, including any appendices or attachments thereof, arehereby incorporated by reference in their entireties.

BACKGROUND

Unless otherwise indicated herein, the approaches described in thissection are not prior art to the claims in this application and are notadmitted to be prior art by inclusion in this section.

A hybrid Frequency Division Duplexing (FDD) and Time Division Duplexing(TDD) wireless network may provide wireless network capability for FDDdevices, TDD devices, and/or hybrid FDD/TDD devices to enable sharedconnectivity on a wireless network. Traditional wireless networks mayonly support one of FDD or TDD. The hybrid FDD/TDD wireless network maybe configured to enable backward compatibility so that legacy devicesand newer hybrid FDD/TDD compatible devices may share network resources.

SUMMARY

In various embodiments, the present disclosure describes example methodsfor wireless communication in a wireless network. Example methods mayinclude transmitting downlink information on a first frequency channelto one or more Frequency Domain Duplex (FDD) User Equipments (UEs).Example methods may include transmitting downlink information on asecond frequency channel during downlink portions of Time DivisionDuplexing (TDD) frame periods of the second frequency channel to one ormore TDD UEs, wherein the second frequency channel is the same frequencychannel on which the one or more FDD UEs are configured to transmit.Example methods may include controlling the uplink transmissions fromthe one or more FDD UEs to occur only during the uplink portions of TDDframe periods.

In various embodiments, the present disclosure describes example methodsfor wireless communication in a wireless network. Example methods mayinclude receiving uplink information on a first frequency channel fromone or more Frequency Domain Duplex (FDD) User Equipments (UEs). Examplemethods may include receiving uplink information on a second frequencychannel during uplink portions of Time Division Duplexing (TDD) frameperiods of the second frequency channel from one or more TDD UEs,wherein the second frequency channel is the same frequency channel asthe frequency channel on which the one or more FDD UEs are configured toreceive downlink transmissions. Example methods may include transmittingdownlink information to the one or more FDD UEs on the second frequencychannel only during downlink portions of TDD frame periods.

In various embodiments, the present disclosure also describes an exampleapparatus for wireless communication. The example apparatus may includea transceiver module configured to connect to one or more antennas. Theexample apparatus may further include a wireless communicationmanagement module communicatively coupled to the transceiver modulecomprising a non-transitory signal bearing medium including instructionswhich, when executed, may transmit downlink information on a firstfrequency channel to one or more Frequency Domain Duplex (FDD) UserEquipments (UEs). The example apparatus may further include instructionswhich, when executed, may transmit downlink information on a secondfrequency channel during downlink portions of Time Division Duplexing(TDD) frame periods of the second frequency channel to one or more TDDUEs, wherein the second frequency channel is the same frequency channelon which the one or more FDD UEs are configured to transmit. The exampleapparatus may further include instructions which, when executed, maycontrol the uplink transmissions from the one or more FDD UEs to occuronly during the uplink portions of TDD frame periods.

In various embodiments, the present disclosure also describes an exampleapparatus for wireless communication. The example apparatus may includea transceiver module configured to connect to one or more antennas. Theexample apparatus may further include a wireless communicationmanagement module communicatively coupled to the transceiver modulecomprising a non-transitory signal bearing medium including instructionswhich, when executed, may receive uplink information on a firstfrequency channel from one or more Frequency Domain Duplex (FDD) UserEquipments (UEs). The example apparatus may further include instructionswhich, when executed, may receive uplink information on a secondfrequency channel during uplink portions of Time Division Duplexing(TDD) frame periods of the second frequency channel from one or more TDDUEs, wherein the second frequency channel is the same frequency channelas the frequency channel on which the one or more FDD UEs are configuredto receive downlink transmissions. The example apparatus may furtherinclude instructions which, when executed, may control transmission ofdownlink information to the one or more FDD UEs on the second frequencychannel to occur only during downlink portions of TDD frame periods.

In various embodiments, the present disclosure also describes an examplearticle for wireless communication by a wireless communicationmanagement module. The example article may include a non-transitorysignal bearing medium comprising machine-readable instructions storedthereon, which, when executed by one or more processors, operativelyenable a node of a wireless network to operate as described herein. Theexample article may include instructions which, when executed, maytransmit downlink information on a first frequency channel to one ormore Frequency Domain Duplex (FDD) User Equipments (UEs). The examplearticle may further include instructions which, when executed, maytransmit downlink information on a second frequency channel duringdownlink portions of Time Division Duplexing (TDD) frame periods of thesecond frequency channel to one or more TDD UEs, wherein the secondfrequency channel is the same frequency channel on which the one or moreFDD UEs are configured to transmit. The example article may furtherinclude instructions which, when executed, may control the uplinktransmissions from the one or more FDD UEs to occur only during theuplink portions of TDD frame periods.

In various embodiments, the present disclosure also describes an examplearticle for wireless communication by a wireless communicationmanagement module. The example article may include a non-transitorysignal bearing medium comprising machine-readable instructions storedthereon, which, when executed by one or more processors, operativelyenable a node of a wireless network to operate as described herein. Theexample article may include instructions which, when executed, mayreceive uplink information on a first frequency channel from one or moreFrequency Domain Duplex (FDD) User Equipments (UEs). The example articlemay further include instructions which, when executed, may receiveuplink information on a second frequency channel during uplink portionsof Time Division Duplexing (TDD) frame periods of the second frequencychannel from one or more TDD UEs, wherein the second frequency channelis the same frequency channel as the frequency channel on which the oneor more FDD UEs are configured to receive downlink transmissions. Theexample article may further include instructions which, when executed,may control transmission of downlink information to the one or more FDDUEs on the second frequency channel to occur only during downlinkportions of TDD frame periods.

The foregoing summary may be illustrative only and may not be intendedto be in any way limiting. In addition to the illustrative aspects,embodiments, and features described above, further aspects, embodiments,and features will become apparent by reference to the drawings and thefollowing detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter is particularly pointed out and distinctly claimed in theconcluding portion of the specification. The foregoing and otherfeatures of the present disclosure will become more fully apparent fromthe following description and appended claims, taken in conjunction withthe accompanying drawings. Understanding that these drawings depict onlyseveral embodiments in accordance with the disclosure and are,therefore, not to be considered limiting of its scope, the disclosurewill be described with additional specificity and detail through use ofthe accompanying drawings.

In the drawings:

FIG. 1 illustrates representations of frequency channels in the time andfrequency domain of an example system for wireless communications usinga Frequency Division Duplexing (FDD) scheme;

FIG. 2 illustrates representations of frequency channels in the time andfrequency domain of an example system for wireless communications usinga Time Division Duplexing (TDD) scheme;

FIG. 3 illustrates representations of frequency channels in the time andfrequency domain of an example system for wireless communications usinga hybrid FDD/TDD scheme;

FIG. 4 illustrates a flow diagram of an example method for wirelesscommunication by a wireless communication management module;

FIG. 5 illustrates a flow diagram of an example method for wirelesscommunication by a wireless communication management module;

FIG. 6 illustrates an example computer program product; and

FIG. 7 illustrates of a block diagram of an example computing device,all arranged in accordance with at least some embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Subject matter is particularly pointed out and distinctly claimed in theconcluding portion of the specification. The foregoing and otherfeatures of the present disclosure will become more fully apparent fromthe following description and appended claims, taken in conjunction withthe accompanying drawings. Understanding that these drawings depict onlyseveral embodiments in accordance with the disclosure and are,therefore, not to be considered limiting of its scope, the disclosurewill be described with additional specificity and detail through use ofthe accompanying drawings.

The following description sets forth various examples along withspecific details to provide a thorough understanding of claimed subjectmatter. It will be understood by those skilled in the art, however, thatclaimed subject matter may be practiced without some or more of thespecific details disclosed herein. Further, in some circumstances,well-known methods, procedures, systems, components and/or circuits havenot been described in detail in order to avoid unnecessarily obscuringclaimed subject matter.

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here. It will be readily understood that the aspects of thepresent disclosure, as generally described herein, and illustrated inthe Figures, can be arranged, substituted, combined, and designed in awide variety of different configurations, all of which are explicitlycontemplated and make part of this disclosure.

This disclosure is drawn, inter alia, to methods, systems andcomputer-readable media related to wireless communications using ahybrid FDD/TDD scheme.

A wireless network may be comprised of one or more base stations thatmay collectively provide wireless data communications services to aplurality of User Equipments (UEs) in a geographical region. In general,a UE may be a communication device used by an end user, such as a mobilephone or the like. In general, providing wireless data communicationsservices may include facilitating wireless communications byfacilitating the transmission and reception of one or more wirelesscommunications. In general, a wireless communication may includeinformation transmitted wirelessly, which may include user data, voicedata, and/or control data. In general, a wireless communication may bedirectional and may be identified as, for example, “a downlinkinformation” (information transmitted by one or more base stations forreception by one or more UEs) and/or “an uplink information”(information transmitted by one or more UEs for reception by one or morebase stations), as appropriate.

In general, wireless data communications may be “full duplex” (i.e.,supporting bidirectional communication). Full duplex operation may beachieved by Frequency Domain Duplexing (FDD) or Time Domain Duplexing(TDD), including techniques disclosed herein. A hybrid FDD/TDD systemmay be configured to support full duplex operation, as further describedherein.

In general, FDD UEs are UEs configured for FDD operation. In general,TDD UEs are UEs configured for TDD operation.

In many cases, TDD may offer better spectral efficiency than FDD, due atleast in part to TDD's ability to adapt to asymmetrical levels ofinformation that need to be carried on the uplink and downlink, asdescribed herein. FDD, on the other hand, offers certain other benefitssuch as lower latency, reduced or eliminated need for transmit andreceive data buffering, and no loss of spectrum efficiency due to arequirement for guard times between transmit and receive time periods.

In accordance with some examples disclosed herein, hybrid FDD/TDD may beemployed to utilize both FDD and TDD as means for duplexing on commonfrequency bands. In some examples, hybrid FDD/TDD systems may provideimproved spectrum efficiency and capacity compared to FDD systems ofcomparable spectrum occupancy while still providing communicationsservice to FDD UEs as well as to TDD UEs.

In some examples, digital wireless networks are communications networkssuch as, for example, cellular networks. In some cases these networksand the UEs that operate on them must be compliant with certain industrystandards to ensure proper interoperation between the wireless networkand the UEs. In some examples, these interoperation standards includedefinitions of different operational requirements for FDD operation andfor TDD operation. In particular, these interoperation standards maydefine certain frequency bands to be used for FDD operation and otherfrequency bands to be used for TDD operation. Current versions of theseinteroperation standards may not provide standards for hybrid FDD/TDDoperation.

In some examples, a wireless network operator may have been allocated,by a government authority, one or more spectrum bands which aredesignated by one or more industry interoperation standards for FDDoperation. In some cases such a network operator may have deployed oneor more FDD networks on this allocated spectrum which provide service toa significant number of users equipped with compatible FDD UEs. In somecases such a network operator may determine that the spectral efficiencyand capacity of one or more of the wireless networks would be enhancedby conversion to hybrid FDD/TDD operation. In doing so, however, it ishighly desirable that the “legacy” FDD UEs currently in use by users ofthe FDD wireless network or networks not be rendered inoperative. Ittherefore follows that it is highly desirable to convert one or more ofthe existing FDD networks to a hybrid FDD/TDD network that is “backwardscompatible” with the “legacy” FDD UEs.

In some examples, a wireless network operator may be allocated by agovernment authority one or more spectrum bands which are designated byone or more industry interoperation standards for FDD operation. In somecases the widespread availability of compatible FDD UEs may stronglyinfluence such a network operator to plan to deploy a network that canprovide service to these compatible FDD UEs, as opposed to some otherkind of UE, for example TDD UEs, which either are not commerciallyavailable or which are not configured to operate on the allocatedspectrum. In some cases such a network operator may determine that thespectral efficiency and capacity of one or more of the planned wirelessnetworks would be enhanced by hybrid FDD/TDD operation. It thereforefollows that in such cases it is highly desirable to deploy a hybridFDD/TDD network that is “backwards compatible” with the widely available“legacy” FDD UEs.

In consideration of the two examples described above, and possibly inother examples, what is needed is a hybrid FDD/TDD system that isbackwards compatible with FDD UEs that are compliant with current orprevious versions of interoperation standards which do not anticipatehybrid FDD/TDD operation. At least some of the embodiments in thepresent disclosure may provide at least some of the benefits of hybridFDD/TDD operation while also providing backwards compatible wirelessdata communications services to such “legacy” FDD UEs.

FIG. 1 illustrates representations of frequency bands in the time andfrequency domain of an example system 100 for wireless communicationsusing a Frequency Division Duplexing (FDD) scheme, arranged inaccordance with at least some industry Interoperation standards. Asshown, system 100 may include paired spectrum bands 110, comprising adownlink frequency band 112 and an uplink frequency band 114, separatedby a guard band 120. The downlink frequency band 112, uplink frequencyband 114, and guard band 120 are represented in the frequency domain byfrequency axis 101 and in the time domain by time axis 102.

In general, the FDD scheme as represented by system 100 may be performedby any type of wireless communications system. In an exemplary case, thesystem 100 may operate in accordance with one of several industrystandards for FDD cellular networks that govern “air interface”interoperation between base stations and FDD UEs. As is well known tothose familiar with the art, these industry standards may include “GSM,”“CDMA,” “W-CDMA,” “UMTS,” “Wi-MAX,” and “LTE.” In accordance with such astandard, base stations transmit on one or more downlink frequencychannels that reside within the downlink frequency band 112 and receiveon one or more uplink frequency channels that reside within the uplinkfrequency band 114. Correspondingly, and also in accordance with such aninteroperation standard, base stations receive on one or more downlinkfrequency channels that reside within the downlink frequency band 112and transmit on one or more uplink frequency channels that reside withinthe uplink frequency band 114. For reasons well known to those familiarwith the art, guard band 120 between downlink frequency band 112 anduplink frequency band 114 makes it practical for base stations and FDDUEs operating in accordance with system 100 to simultaneously transmitand receive without the need for filters or other means of excessivecomplexity and cost.

In some examples, the FDD scheme as represented by system 100 may beexecuted or controlled by a wireless communication management module ata base station. In some examples, the FDD scheme may be executed orcontrolled by a wireless communication management module at a UE.

In general, as used herein “frequency channel” refers to a portion ofradio frequency (RF) spectrum designated for transmission of informationbetween radio base station and UEs. The term “frequency channel” doesnot imply any format, modulation, coding, or segmentation of thatportion of the RF spectrum, although a particular interoperationstandard may prescribe one or more of such characteristics to adesignated frequency channel.

Paired spectrum 110 may be allocated according to government policy orother functionality that prescribes policies of spectrum utilization. Insome cases, by virtue of its inclusion of two frequency bands separatedby a guard band, such an allocation may be made in anticipation of itsuse for FDD wireless networks. In some cases industry interoperationstandards take into consideration existing or anticipated pairedspectrum allocations by defining FDD operation for them. In some casesinteroperation standards for FDD wireless systems may define one or moredownlink frequency channels within the downlink frequency band and oneor more uplink frequency channels within the uplink frequency band. Insome cases there is a one-to-one correspondence between paired frequencychannels in the uplink and downlink frequency bands, and in some casesthe frequency separation between such paired frequency channels is aconstant. In other cases there may be no correspondence between uplinkfrequency channels and downlink frequency channels.

In some cases the operation of FDD UEs operating in accordance withsystem 100 will be prescribed by one or more interoperation standards.In some cases such prescribed operation will include operation of the UEin the frequency domain 101 and in the time domain 102. For example,interoperation standards may allow or require an “idle” UE tocontinuously or intermittently receive a downlink control channel so asto receive information transmitted to it by one or more serving basestations. In another example, interoperation standards may allow orrequire a UE to transmit on a particular uplink access channel as partof a call initiation process or other function. In this example, in somecases the UE may be allowed or required to make such access channeltransmissions within one or more of a sequence of prescribed periods inthe time domain 102, and in other cases the UE may be allowed orrequired to make such access channel transmissions at any time.

The above-cited example of FDD EU transmission on an uplink accesschannel may be considered to be one of a class of UE uplinktransmissions that are “autonomous.” Autonomous FDD UE transmissions arethose which may be made on one or more uplink frequency channels in atleast one of the following two organizations with respect to time domain102: (a) at any time; and (b) within one or more of a prescribedsequence of time periods, but not limited to any particular one or moreof such a sequence of time periods. Thus, from the perspective of one ormore base stations receiving autonomous transmissions from FDD UEs, suchautonomous transmissions may occur, respectively: (a) at any time; or(b) within any of the prescribed sequence of time periods.

As is well understood by those familiar with the art, operation of FDDUEs in accordance with one or more interoperation standards may becontrolled in part by downlink control messages transmitted by one ormore base stations. In some cases such downlink control messages mayinclude messages which are transmitted to, and are intended to control,a particular UE. In other cases such downlink control messages mayinclude messages which are transmitted to, and are intended to control,either a plurality of UEs or all UEs that receive them. In some cases,downlink control messages may control one or a plurality of FDD UEs withrespect to their operation in the frequency domain 101 and in the timerdomain 102. In some cases one or more downlink control messages,commonly called channel assignment messages, may instruct one or moreFDD UEs to transmit on a particular uplink frequency channel within theuplink frequency band 114 and/or to receive on a particular downlinkchannel within the downlink frequency band 112. In some cases one ormore downlink control messages may instruct one or more FDD UEs totransmit and/or receive only during one or more specific time periods inthe time domain 102.

As is also well understood by those familiar with the art, operation ofFDD UEs in some examples may be modified in at least some respects bychanging or reprogramming of the software and/or firmware residentwithin those UEs through a process commonly referred to as “over-the-airprogramming” (OTAP). In OTAP, new programming, and in some casesinstructions for its implementation, are conveyed to one or more UEs, inaccordance with one or more interoperation standards, through theserving wireless network. OTAP thus provides a practical means by whichlarge numbers of UEs already “in the field” can be reprogrammed withouta requirement that they individually be physically brought or remotelyconnected to a reprogramming system.

In some examples, OTAP may be useful for making UEs recognize andproperly respond to newly defined downlink control messages. However, insome examples certain operational characteristics of UEs may not bechangeable using OTAP. In some examples UE characteristics that cannotbe changed using OTAP may include frequency bands on which they canoperate. In some examples OTAP may not be usable to enable an FDD UE tooperate as a TDD UE.

FDD system 100 may provide for communication of information in both theuplink and downlink. In some cases, network traffic may be asymmetric,meaning that the amount of traffic in the downlink is greater than theamount of traffic in the uplink, or vice versa. In some cases thisasymmetry may be of a magnitude such that, for example, the downlinkfrequency band 112 may be overloaded, resulting in poor service quality,while the uplink frequency band has unutilized capacity. In someexamples, it may be desirable to account for an asymmetry in networktraffic, for example by allocating/providing more bandwidth in thedownlink direction than in the uplink direction (or vice versa). In someexamples, the system 100 including allocated FDD frequency bands 110 mayhave a bandwidth asymmetry that may be fixed at any ratio, and/or may beadjustable to any ratio. However, because the allocated FDD frequencybands may be fixed by government regulations and/or by industryinteroperation standards, in some examples it may not be possible toadjust the bandwidth asymmetry.

FIG. 2 illustrates representations of a frequency band of an examplesystem 200 for wireless communications using a Time Division Duplexing(TDD) scheme, arranged in accordance with at least some industryInteroperation standards. As shown, system 200 may include a single TDDfrequency band 220. TDD frequency band 220 may be comprised ofconcatenated frame periods 210. Each frame period 210 may include adownlink period 222 and an uplink period 223 separated by an intra-frameguard time 212, and an inter-frame guard time 214. In each frame period210 the downlink period 222 may precede the uplink period 223 as shown,or their order may be reversed. The inter-frame guard time 214 may be ofthe same duration as the intra-frame guard time 212 or of a differentduration, and may occur at the end of the frame period 210 as shown orat its beginning. The frequency band 220 is represented in the frequencydomain by frequency axis 201 and in the time domain by time axis 202. Insome examples, TDD communication as shown in system 200 may be executedor controlled by a wireless communication management module at a basestation. In some examples, TDD communication may be executed orcontrolled by a wireless communication management module at a UE.

The TDD scheme as shown in system 200 may provide wireless communicationusing TDD frequency band 220. In an exemplary case, the system 200 mayoperate in accordance with one of several industry standards for TDDcellular networks that govern “air interface” interoperation betweenbase stations and TDD UEs. As is well known to those familiar with theart, these industry standards may include “CDMA,” “W-CDMA,” “UMTS,”“Wi-MAX,” and “LTE.”

In general, TDD frequency band 220 may be allocated according togovernment policy or other functionality that prescribes policies ofspectrum utilization. In some cases, by virtue of its absence of twofrequency bands separated by a guard band, such an allocation may bemade in anticipation of its use for TDD wireless networks rather thanfor FDD networks. In some cases industry interoperation standards takeinto consideration existing or anticipated spectrum allocations of thistype, that are not suitable for FDD use, by defining TDD operation forthem.

In general, downlink period 222 may be used for communication ofinformation transmitted by one or more base stations for reception byone or more TDD UEs. In some examples, downlink period 222 may also bereferred to as a forward communication period. In general, uplink period223 may be used for communication of information transmitted by one ormore TDD UEs for reception by one or more base stations. In someexamples, uplink period 223 may also be referred to as a reversecommunication period. In some examples, a TDD frequency band maycomprise one or more frequency channels designated for uplinkcommunications during uplink periods and one or more frequency channelsdesignated for downlink communications during downlink periods.

In some examples, the TDD frequency band 220 may occupy a contiguousblock of spectrum or may occupy two or more blocks of spectrum. In someexamples the bandwidth occupied by the TDD frequency band, representedby the difference between the lowest and highest frequency therein, isof sufficient narrowness that, for reasons well known to those familiarwith the art, base stations and UEs of practical design cannotsimultaneously transmit and receive on any frequency channels withinthat frequency band. The TDD scheme as shown in system 200 may includeguard times 212 and 214 to accommodate signal propagation between a basestation and its most distant served UE and thus to avoid interferencebetween downlink communication and uplink communication. In someexamples, the duration of guard times 212 and/or 214 may be adjusted toavoid interference between downlink communication and uplinkcommunication. In some examples this adjustment is comprised ofincreasing or decreasing one or both of the downlink period and theuplink period so that the frame period remains constant. In otherexamples the adjustment may include a change in the frame period.

In some examples the relative durations of downlink period 222 anduplink period 223 may be adjusted, at least in part to accommodateasymmetry between downlink and uplink traffic loading. In some examplesthis adjustment is comprised of increasing one of the downlink periodand the uplink period while decreasing the other by a comparable amountso that the frame period remains constant. In other examples theadjustment may include a change in the frame period.

In some cases the operation of TDD UEs operating in accordance withsystem 200 will be prescribed by one or more interoperation standards.In some examples, interoperation standards may allow or require a TDD UEto transmit on a particular uplink access channel as part of a callinitiation process or other function. In this example, in some cases theUE may be allowed or required to make such access channel transmissionswithin one or more of a sequence of prescribed periods in the timedomain 202 which occur during uplink periods 223, and in other cases theUE may be allowed or required to make such access channel transmissionsat any time during uplink periods 223.

The above-cited example of TDD EU transmission on an uplink accesschannel may be considered to be one of a class of UE uplinktransmissions that are “autonomous.” Autonomous TDD UE transmissions arethose which may be made on one or more uplink frequency channels in atleast one of the following two organizations with respect to time domain202: (a) at any time during one or more uplink periods; and (b) withinone or more of a prescribed sequence of time periods (all of which occurduring uplink periods), but not limited to any particular one or more ofsuch a sequence of time periods. Thus, from the perspective of one ormore base stations receiving autonomous transmissions from TDD UEs, suchautonomous transmissions may occur, respectively: (a) at any time duringone or more uplink periods; or (b) within any of the prescribed sequenceof time periods within uplink periods.

As is well understood by those familiar with the art, operation of TDDUEs in accordance with one or more interoperation standards may becontrolled in part by downlink control messages transmitted by one ormore base stations. In some cases such downlink control messages mayinclude messages which are transmitted to, and are intended to control,a particular UE. In other cases such downlink control messages mayinclude messages which are transmitted to, and are intended to control,either a plurality of UEs or all UEs that receive them. In some cases,downlink control messages may control one or a plurality of TDD UEs withrespect to their operation in the frequency domain 201 and in the timedomain 202. In some cases one or more downlink control messages,commonly called channel assignment messages, may instruct one or moreTDD UEs to transmit on a particular uplink frequency channel within theuplink period 223 and/or to receive on a particular downlink channelwithin the downlink period 222. In some cases one or more downlinkcontrol messages may instruct one or more TDD UEs to transmit and/orreceive during one or more specific time periods in the time domain 202.In some cases one or more downlink control messages may inform one ormore TDD UEs as to durations of one or more of frame period, downlinkperiod, uplink period, intra-frame guard time, and inter-frame guardtime.

FIG. 3 illustrates representations of frequency bands in the time andfrequency domain of an example system 300 for wireless communicationsusing a hybrid FDD/TDD scheme providing enhanced downlink capacity,arranged in accordance with at least some embodiments of the presentdisclosure. As shown, system 300 may include downlink frequency band112, hybrid TDD frequency band 320, and guard band 120. The downlinkfrequency band 112, hybrid TDD frequency band 320, and guard band 120are represented in the frequency domain by frequency axis 301 and in thetime domain by time axis 302.

Hybrid TDD frequency band 320 may be comprised of concatenated frameperiods 310. Each frame period 310 may include a downlink period 322 andan uplink period 323 separated by an intra-frame guard time 312, and aninter-frame guard time 314. Frame period 310, downlink period 322,uplink period 323, intra-frame guard time 312, and inter-frame guardtime 314 have generally the same function and characteristics as theircounterparts in TDD frequency band 220 as depicted in FIG. 2 and hereindescribed with respect thereto.

In some examples, a hybrid FDD/TDD system comprising the frequency bandsof system 300 can provide communications services to both FDD UEs andTDD UEs. In some examples, FDD UEs so served will receive downlinkinformation on frequency channels within the downlink frequency band112, and TDD UEs so served will receive downlink information withindownlink periods on frequency channels within the hybrid TDD frequencyband 320. In some examples Both FDD UEs and TDD UEs will transmit uplinkinformation within uplink periods on frequency channels within thehybrid TDD frequency band 320.

In some examples of system 300 as arranged in accordance with at leastsome embodiments of the present disclosure, downlink frequency band 112occupies the same spectrum, and operates in essentially the same manner,as the downlink frequency band of a system heretofore operating as anFDD system as shown in FIG. 1. In some examples, the downlink frequencyband 112 of system 300 may operate in accordance with relevant portionsof one or more current interoperation standards for FDD networks exceptfor certain additional requirements. In some examples, these additionalrequirements may include a requirement for modification of existingstandardized control protocols, or promulgation of new standardizedcontrol protocols. In some examples, these modified or new controlprotocols control operation of FDD UEs operating on the hybrid FDD/TDDnetwork so that their uplink transmissions are compatible with operationon the hybrid TDD frequency band 320 as described herein. Processes bywhich existing control protocols can be modified and/or new controlprotocols can be promulgated are well known to those familiar with theart.

In some examples of system 300 as arranged in accordance with at leastsome embodiments of the present disclosure, hybrid TDD frequency band320 occupies the same spectrum as the uplink frequency band 114 of asystem heretofore operating as an FDD system as shown in FIG. 1. In someexamples of system 300 as arranged in accordance with at least someembodiments of the present disclosure, hybrid TDD frequency band 320 mayoperate essentially in accordance with relevant portions of one or morecurrent interoperation standards for TDD networks except that it mayoccupy spectrum that is not designated for TDD operation. In otherexamples hybrid TDD frequency band 320 may operate in accordance withrelevant portions of new interoperation standards for hybrid FDD/TDDnetworks.

In some examples, a “legacy” FDD UE may operate on a hybrid FDD/TDDnetwork in accordance with system 300 so long as (a) the FDD UE's uplinktransmissions are controlled so as to occur only during uplink periodsof the hybrid TDD frequency band 320 and (b) uplink operation of the UEis otherwise compatible with requirements of interoperation standardsfor hybrid FDD/TDD networks. In some examples hybrid FDD/TDDinteroperation standards can advantageously be drawn to promote suchbackwards compatibility with legacy FDD UEs by defining hybrid TDDfrequency band organization and operation as closely as possible to theFDD uplink frequency band as defined by one or more currentinteroperation standards for FDD networks.

In some examples, a “legacy” FDD UE may be reconfigured to enable itsoperation on a hybrid FDD/TDD network in accordance with system 300 byreprogramming its firmware and/or software. In some examples thisreprogramming may include implementation of changes or additions to oneor more processes whereby the UE recognizes when it is operating in ahybrid FDD/TD network and thereupon configures its uplink operation soas to be compatible with operation on the hybrid TDD frequency band 320.In some examples this uplink operation configuration may includeexecution of autonomous transmissions such that they are in the form ofTDD UE autonomous transmissions in compliance with one or moreinteroperation standards for hybrid FDD/TDD networks. In some examplesthe reprogramming of FDD UE firmware and/or software may enable the UEto recognize and properly respond to modified or new downlink controlmessage protocols in compliance with one or more interoperationstandards for hybrid FDD/TDD networks. In some examples thereprogramming of FDD UE firmware and/or software may be accomplishedusing OTAP.

In some examples, added downlink capacity enabled by reconfiguring anFDD network to a hybrid FDD/TDD network cam be exploited by introductionof TDD UEs, either as replacements for some of the legacy FDD UEsheretofore operating on the network, to equip new users, or acombination of both. In some examples the configuration and operation ofthe hybrid TDD frequency band 320 will be essentially in conformancewith one or more existing interoperation standards for TDD networksexcept that it may occupy spectrum that is not designated for TDDnetwork operation. In some of such cases the introduced TDD UEs mayinclude those that are compliant with one or more existinginteroperation standards for TDD networks, possibly after beingreprogrammed to operate on TDD frequency band 320. In other examples theconfiguration and operation of the hybrid frequency band 320 will not bein conformance with one or more existing interoperation standards forTDD networks. In some of such cases the introduced TDD UEs may have tobe of new design compliant with one or more interoperation standards forhybrid FDD/TDD networks.

In some examples, the spectral efficiency and capacity of hybrid FDD/FDDnetworks may be optimized by adjusting the relative durations ofdownlink periods 222 and uplink periods 223 so as to accommodate therelative levels of downlink and uplink traffic loads on the hybrid TDDfrequency band 320. In some examples spectral efficiency and capacitymay also be optimized by adjusting the mix of FDD UEs and TD UEsdeployed for operation on the network. In some examples some of the UEsserved by the network may be capable of changing configuration betweenFDD and TDD operation according to control instructions received fromone or more base stations, in some of which cases spectral efficiencyand capacity of the network may be optimized by controlling theconfigurations of some or all such UEs.

As shown in FIG. 3, system 300 includes the frequency band organizationof a Hybrid TDD/FDD system that is configured to accommodateasymmetrical loading between the uplink and downlink wherein thedownlink is more heavily loaded than the uplink. This is currently themost common case in wireless networks used primarily for datacommunications. However, it will be appreciated by those familiar withthe art that some wireless networks may carry more traffic in the uplinkthan in the downlink, in which case a hybrid FDD/TDD network mightadvantageously include an uplink frequency band, rather than a downlinkfrequency band, in addition to the hybrid TDD band 320. From the hybridFDD/TDD scheme shown in FIG. 3 and herein described, those familiar withthe art will readily understand the configuration, operation, andpotential backwards compatibility with legacy FDD UEs of a hybridFDD/TDD scheme that includes an uplink frequency band rather than adownlink frequency band.

In some examples, the hybrid FDD/TDD scheme may be executed orcontrolled by a wireless communication management module at a basestation. In some examples, the hybrid FDD/TDD scheme may be executed orcontrolled by a wireless communication management module at a UE.

In some examples, a hybrid TDD frequency band 320 may be created byreconfiguration of the FDD uplink frequency band 114 of a networkformerly configured in accordance with one or more interoperationstandards for FDD networks. In some examples, such reconfiguration of anFDD network to a hybrid FDD/TDD network may promote spectrum efficiencyand/or enhance network capacity by repurposing heretofore underutilizeduplink spectrum to provide downlink capacity. In some examples theseimprovements are rendered more practical and cost-effective by allowinglegacy FDD UEs to continue to operate in the resulting hybrid FDD/TDDscheme.

FIG. 4 illustrates a flow diagram of an example method 400 for wirelesscommunication, arranged in accordance with at least some embodiments ofthe present disclosure. In general, method 400 may be performed by anysuitable device, devices, or systems such as those discussed herein. Insome examples, a base station may perform method 400. In some examples,a UE may perform method 400. In some examples, a wireless communicationmanagement module may perform method 400.

Method 400 sets forth various functional blocks or actions that may bedescribed as processing steps, functional operations, events and/oracts, etc., which may be performed by hardware, software, and/orfirmware. Numerous alternatives to the functional blocks shown in FIG. 4may be practiced in various implementations. For example, interveningactions not shown and/or additional actions not shown may be employedand/or some of the actions shown may be eliminated, without departingfrom the scope of claimed subject matter. In some examples, the actionsshown in one figure may be operated using techniques discussed withrespect to another figure. Additionally, in some examples, the actionsshown in these figures may be operated using parallel processingtechniques. The above described, and others not described,rearrangements, substitutions, changes, modifications, etc., may be madewithout departing from the scope of claimed subject matter. Method 400may include one or more of functional operations as indicated by one ormore of blocks 410, 420, and/or 430. The process of method 400 may beginat block 410.

At block 410, “Transmit downlink information on a first frequencychannel to one or more Frequency Domain Duplex (FDD) User Equipments(UEs)”, downlink information may be transmitted on a first frequencychannel to one or more FDD UEs. In general, the downlink information maybe transmitted to FDD UEs using any suitable technique or techniques.

In general, an FDD UE of the one or more FDD UEs may be a legacycommunication device or a device compatible with hybrid FDD/TDDcommunication. As described herein, some legacy communication devicesmay not be capable of transmitting and/or receiving TDD communications.

Process of method 400 may continue from block 410 to block 420.

At block 420, “Transmit downlink information on a second frequencychannel during downlink portions of Time Domain Duplex (TDD) frameperiods of the second frequency channel to one or more TDD UEs, whereinthe second frequency channel is the same frequency channel as thefrequency channel on which the FDD UEs are configured to transmit”,downlink information may be transmitted on a second frequency channelduring downlink portions of TDD frame periods of the second frequencychannel to one or more TDD UEs. The second frequency channel may be thesame frequency channel as the frequency channel on which the FDD UEs areconfigured to transmit. In general, the downlink information may betransmitted using any suitable technique or techniques. In general, thefirst frequency channel may reside within a first frequency band and thesecond frequency channel may reside within a second frequency band,wherein the second frequency band may be separated from the firstfrequency band by a guard band. In some examples, the second frequencychannel may comprise concatenated TDD frame periods, each having adownlink period for downlink communication and an uplink period foruplink communication. In general, the downlink period and uplink periodmay be separated by an intra-frame guard time and/or an inter-frameguard time. Process of method 400 may continue from block 420 to block430.

At block 430, “Control the uplink transmissions from the FDD UEs tooccur only during uplink portions of TDD frame periods of the secondfrequency channel”, uplink transmissions originating from the FDD UEsmay be controlled to occur only during uplink portions of TDD frameperiods of the second frequency channel. Process of method 400 may stopafter block 430.

FIG. 5 illustrates a flow diagram of an example method 500 for wirelesscommunication, arranged in accordance with at least some embodiments ofthe present disclosure. In general, method 500 may be performed by anysuitable device, devices, or systems such as those discussed herein. Insome examples, a base station may perform method 500. In some examples,a UE may perform method 500. In some examples, a wireless communicationmanagement module may perform method 500.

Method 500 sets forth various functional blocks or actions that may bedescribed as processing steps, functional operations, events and/oracts, etc., which may be performed by hardware, software, and/orfirmware. Numerous alternatives to the functional blocks shown in FIG. 5may be practiced in various implementations. For example, interveningactions not shown and/or additional actions not shown may be employedand/or some of the actions shown may be eliminated, without departingfrom the scope of claimed subject matter. In some examples, the actionsshown in one figure may be operated using techniques discussed withrespect to another figure. Additionally, in some examples, the actionsshown in these figures may be operated using parallel processingtechniques. The above described, and others not described,rearrangements, substitutions, changes, modifications, etc., may be madewithout departing from the scope of claimed subject matter. Method 500may include one or more of functional operations as indicated by one ormore of blocks 510, 520, and/or 530. The process of method 500 may beginat block 510.

At block 510, “Receive uplink information on a first frequency channelfrom one or more Frequency Domain Duplex (FDD) User Equipments (UEs)”,uplink information may be received on a first frequency channel from oneor more FDD UEs. In general, the uplink information may be transmittedfrom FDD UEs using any suitable technique or techniques.

In general, an FDD UE of the one or more FDD UEs may be a legacycommunication device or a device compatible with hybrid FDD/TDDcommunication. As described herein, some legacy communication devicesmay not be capable of transmitting and/or receiving TDD communications.

Process of method 500 may continue from block 510 to block 520.

At block 520, “Receive uplink information on a second frequency channelduring uplink portions of Time Domain Duplex (TDD) frame periods of thesecond frequency channel from one or more TDD UEs, wherein the secondfrequency channel is the same frequency channel as the frequency channelon which the FDD UEs are configured to receive downlink transmissions”,uplink information may be received on a second frequency channel duringuplink portions of TDD frame periods of the second frequency channelfrom one or more TDD UEs. The second frequency channel may be the samefrequency channel as the frequency channel on which the FDD UEs areconfigured to receive downlink transmissions. In general, the uplinkinformation may be received using any suitable technique or techniques.In general, the first frequency channel may reside within a firstfrequency band and the second frequency channel may reside within asecond frequency band, wherein the second frequency band may beseparated from the first frequency band by a guard band. In someexamples, the second frequency channel may comprise concatenated TDDframe periods, each having a downlink period for downlink communicationand an uplink period for uplink communication. In general, the downlinkperiod and uplink period may be separated by an intra-frame guard timeand/or an inter-frame guard time. Process of method 500 may continuefrom block 520 to block 530.

At block 530, “Transmit downlink information to the one or more FDD UEson the second frequency channel only during downlink portions of TDDframe periods”, downlink transmissions originating from the FDD UEs maybe transmitted only during downlink portions of TDD frame periods of thesecond frequency channel. Process of method 500 may stop after block530.

FIG. 6 illustrates an example computer program product 600, arranged inaccordance with at least some embodiments of the present disclosure.Computer program product 600 may include machine readable non-transitorymedium having stored therein instructions that, when executed, cause themachine to manage wireless communications according to the processes andmethods discussed herein. Computer program product 600 may include asignal bearing medium 602. Signal bearing medium 602 may include one ormore machine-readable instructions 604, which, when executed by one ormore processors, may operatively enable a computing device to providethe functionality described herein. Signal bearing medium 602 mayinclude one or more machine-readable instructions 605, which, whenexecuted by one or more processors, may operatively enable a computingdevice to provide the functionality described herein. In variousexamples, some or all of the machine-readable instructions may be usedby the devices discussed herein.

In some examples, the machine readable instructions 604 may includeinstructions that, when executed, may operatively enable a wirelesscommunication management module to transmit downlink information on afirst frequency channel to one or more Frequency Domain Duplex (FDD)User Equipments (UEs). In general, the downlink information may betransmitted to FDD UEs using any suitable technique or techniques.

In some examples, the machine readable instructions 604 may includeinstructions that, when executed, may operatively enable a wirelesscommunication management module to transmit downlink information on asecond frequency channel during downlink portions of Time Domain Duplex(TDD) frame periods of the second frequency channel to one or more TDDUEs, wherein the second frequency channel is the same frequency channelas the frequency channel on which the FDD UEs are configured totransmit. In general, the downlink information may be transmitted usingany suitable technique or techniques. In general, the first frequencychannel may reside within a first frequency band and the secondfrequency channel may reside within a second frequency band, wherein thesecond frequency band may be separated from the first frequency band bya guard band. In some examples, the second frequency channel maycomprise concatenated TDD frame periods, each having a downlink periodfor downlink communication and an uplink period for uplinkcommunication. In general, the downlink period and uplink period may beseparated by an intra-frame guard time and/or an inter-frame guard time.

In some examples, the machine readable instructions 604 may includeinstructions that, when executed, may operatively enable a wirelesscommunication management module to control the uplink transmissions fromthe FDD UEs to occur only during uplink portions of TDD frame periods ofthe second frequency channel.

In some examples, the machine readable instructions 605 may includeinstructions that, when executed, may operatively enable a wirelesscommunication management module to receive uplink information on a firstfrequency channel from one or more Frequency Domain Duplex (FDD) UserEquipments (UEs). In general, the uplink information may be transmittedfrom FDD UEs using any suitable technique or techniques.

In some examples, the machine readable instructions 605 may includeinstructions that, when executed, may operatively enable a wirelesscommunication management module to receive uplink information on asecond frequency channel during uplink portions of Time Domain Duplex(TDD) frame periods of the second frequency channel from one or more TDDUEs, wherein the second frequency channel is the same frequency channelas the frequency channel on which the FDD UEs are configured to receivedownlink transmissions. In general, the uplink information may bereceived using any suitable technique or techniques. In general, thefirst frequency channel may reside within a first frequency band and thesecond frequency channel may reside within a second frequency band,wherein the second frequency band may be separated from the firstfrequency band by a guard band. In some examples, the second frequencychannel may comprise concatenated TDD frame periods, each having adownlink period for downlink communication and an uplink period foruplink communication. In general, the downlink period and uplink periodmay be separated by an intra-frame guard time and/or an inter-frameguard time.

In some examples, the machine readable instructions 605 may includeinstructions that, when executed, may operatively enable a wirelesscommunication management module to transmit downlink information to theone or more FDD UEs on the second frequency channel only during downlinkportions of TDD frame periods.

In some implementations, signal bearing medium 602 may encompass acomputer-readable medium 606, such as, but not limited to, a hard diskdrive, a Compact Disc (CD), a Digital Versatile Disk (DVD), a digitaltape, memory, etc. In some implementations, signal bearing medium 602may encompass a recordable medium 608, such as, but not limited to,memory, read/write (R/W) CDs, R/W DVDs, etc. In some implementations,signal bearing medium 602 may encompass a communications medium 610,such as, but not limited to, a digital and/or an analog communicationmedium (e.g., a fiber optic cable, a waveguide, a wired communicationlink, a wireless communication link, etc.). In some examples, signalbearing medium 602 may encompass a machine readable non-transitorymedium.

FIG. 7 is a block diagram illustrating an example computing device 700,arranged in accordance with at least some embodiments of the presentdisclosure. In various examples, computing device 700 may be configuredto manage wireless communications as discussed herein. In one examplebasic configuration 701, computing device 700 may include one or moreprocessors 710 and system memory 720. A memory bus 730 can be used forcommunicating between the processor 710 and the system memory 720.

Depending on the desired configuration, processor 710 may be of any typeincluding but not limited to a microprocessor (μP), a microcontroller(μC), a digital signal processor (DSP), or any combination thereof.Processor 710 can include one or more levels of caching, such as a levelone cache 711 and a level two cache 712, a processor core 713, andregisters 714. The processor core 713 can include an arithmetic logicunit (ALU), a floating point unit (FPU), a digital signal processingcore (DSP core), or any combination thereof. A memory controller 715 canalso be used with the processor 710, or in some implementations thememory controller 715 can be an internal part of the processor 710.

Depending on the desired configuration, the system memory 720 may be ofany type including but not limited to volatile memory (such as RAM),non-volatile memory (such as ROM, flash memory, etc.) or any combinationthereof. System memory 720 may include an operating system 721, one ormore applications 722, and program data 724. Application 722 may includewireless communication management application 723 that can be arrangedto perform the functions, actions, and/or operations as described hereinincluding the functional blocks, actions, and/or operations describedherein. Program Data 724 may include wireless communication managementdata (725) for use with wireless communication management application723. In some example embodiments, application 722 may be arranged tooperate with program data 724 on an operating system 721. This describedbasic configuration is illustrated in FIG. 7 by those components withindashed line 701.

Computing device 700 may have additional features or functionality, andadditional interfaces to facilitate communications between the basicconfiguration 701 and any required devices and interfaces. For example,a bus/interface controller 740 may be used to facilitate communicationsbetween the basic configuration 701 and one or more data storage devices750 via a storage interface bus 741. The data storage devices 750 may beremovable storage devices 751, non-removable storage devices 752, or acombination thereof. Examples of removable storage and non-removablestorage devices include magnetic disk devices such as flexible diskdrives and hard-disk drives (HDD), optical disk drives such as compactdisk (CD) drives or digital versatile disk (DVD) drives, solid statedrives (SSD), and tape drives to name a few. Example computer storagemedia may include volatile and nonvolatile, removable and non-removablemedia implemented in any method or technology for storage ofinformation, such as computer readable instructions, data structures,program modules, or other data.

System memory 720, removable storage 751 and non-removable storage 752are all examples of computer storage media. Computer storage mediaincludes, but is not limited to, RAM, ROM, EEPROM, flash memory or othermemory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which maybe used to store the desired information and which may be accessed bycomputing device 700. Any such computer storage media may be part ofdevice 700.

Computing device 700 may also include an interface bus 742 forfacilitating communication from various interface devices (e.g., outputinterfaces, peripheral interfaces, and communication interfaces) to thebasic configuration 701 via the bus/interface controller 740. Exampleoutput interfaces 760 may include a graphics processing unit 761 and anaudio processing unit 762, which may be configured to communicate tovarious external devices such as a display or speakers via one or moreA/V ports 763. Example peripheral interfaces 770 may include a serialinterface controller 771 or a parallel interface controller 772, whichmay be configured to communicate with external devices such as inputdevices (e.g., keyboard, mouse, pen, voice input device, touch inputdevice, etc.) or other peripheral devices (e.g., printer, scanner, etc.)via one or more I/O ports 773. An example communication interface 780includes a network controller 781, which may be arranged to facilitatecommunications with one or more other computing devices 783 over anetwork communication via one or more communication ports 782. Acommunication connection is one example of a communication media.Communication media may typically be embodied by computer readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. A “modulateddata signal” may be a signal that has one or more of its characteristicsset or changed in such a manner as to encode information in the signal.By way of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), infrared (IR) andother wireless media. The term computer readable media as used hereinmay include both storage media and communication media.

Computing device 700 may be implemented as a portion of a small-formfactor portable (or mobile) electronic device such as a cell phone, amobile phone, a tablet device, a laptop computer, a personal dataassistant (PDA), a personal media player device, a wireless web-watchdevice, a personal headset device, an application specific device, or ahybrid device that includes any of the above functions. Computing device700 may also be implemented as a personal computer including both laptopcomputer and non-laptop computer configurations. In addition, computingdevice 700 may be implemented as part of a wireless base station orother wireless system or device.

Some portions of the foregoing detailed description are presented interms of algorithms or symbolic representations of operations on databits or binary digital signals stored within a computing system memory,such as a computer memory. These algorithmic descriptions orrepresentations are examples of techniques used by those of ordinaryskill in the data processing arts to convey the substance of their workto others skilled in the art. An algorithm is here, and generally, isconsidered to be a self-consistent sequence of operations or similarprocessing leading to a desired result. In this context, operations orprocessing involve physical manipulation of physical quantities.Typically, although not necessarily, such quantities may take the formof electrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals or the like. It should be understood, however, that all ofthese and similar terms are to be associated with appropriate physicalquantities and are merely convenient labels. Unless specifically statedotherwise, as apparent from the following discussion, it is appreciatedthat throughout this specification discussions utilizing terms such as“processing,” “computing,” “calculating,” “determining” or the likerefer to actions or processes of a computing device, that manipulates ortransforms data represented as physical electronic or magneticquantities within memories, registers, or other information storagedevices, transmission devices, or display devices of the computingdevice.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In some embodiments,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a flexible disk, a hard disk drive (HDD), a Compact Disc(CD), a Digital Versatile Disk (DVD), a digital tape, a computer memory,etc.; and a transmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunication link, a wireless communication link, etc.).

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely examples and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claimed subject matter containing onlyone such recitation, even when the same claim includes the introductoryphrases “one or more” or “at least one” and indefinite articles such as“a” or “an” (e.g., “a” and/or “an” should typically be interpreted tomean “at least one” or “one or more”); the same holds true for the useof definite articles used to introduce claim recitations. In addition,even if a specific number of an introduced claim recitation isexplicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

While certain example techniques have been described and shown hereinusing various methods and systems, it should be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein. Therefore, it isintended that claimed subject matter not be limited to the particularexamples disclosed, but that such claimed subject matter also mayinclude all implementations falling within the scope of the appendedclaims, and equivalents thereof.

What is claimed is:
 1. A method for wireless communication in a wirelessnetwork, the method comprising: transmitting downlink information on afirst frequency channel to one or more frequency domain duplex (FDD)user equipments (UEs); transmitting downlink information on a secondfrequency channel during downlink portions of time domain duplex (TDD)frame periods of the second frequency channel to one or more TDD UEs,wherein the second frequency channel is a frequency channel on which theFDD UEs are configured to transmit uplink information; and controllinguplink transmissions, to transmit the uplink information on the secondfrequency channel, from the FDD UEs to occur during uplink portions ofthe TDD frame periods of the second frequency channel, wherein theuplink portions, during which the FDD UEs transmit the uplinkinformation, are distinct from the downlink portions, during which theTDD UEs receive the downlink information, of the TDD frame periods. 2.The method of claim 1, further comprising: prior to transmitting thedownlink information on the second frequency channel, reconfiguring thefrequency channel on which the FDD UEs are configured to transmit theuplink information as the second frequency channel.
 3. The method ofclaim 1, further comprising: dynamically modifying at least one of atime interval of the TDD frame periods, a time interval of the downlinkportions of the TDD frame periods, or a time interval of the uplinkportions of the TDD frame periods.
 4. The method of claim 1, wherein thewireless network includes a long term evolution (LTE) wireless network.5. The method of claim 1, wherein the wireless network includes acellular network.
 6. The method of claim 1, wherein at least one of theFDD UEs includes a headset.
 7. The method of claim 1, wherein at leastone of the FDD UEs includes a mobile phone.
 8. An apparatus for wirelesscommunication, the apparatus comprising: a transceiver operable toestablish a communication like with one or more antennas; a processorcoupled to the transceiver; and a non-transitory computer-readablemedium coupled to the processor and having instructions stored thereon,which in response to execution by the processor, cause the processor toperform or control performance of operations that include: transmit, viathe transceiver, downlink information on a first frequency channel toone or more frequency domain duplex (FDD) user equipments (UEs);transmit, via the transceiver, downlink information on a secondfrequency channel during downlink portions of time domain duplex (TDD)frame periods of the second frequency channel to one or more TDD UEs,wherein the second frequency channel is a frequency channel on which theFDD UEs are configured to transmit uplink information; and controluplink transmissions, to transmit the uplink information on the secondfrequency channel, from the FDD UEs to occur during uplink portions ofthe TDD frame periods of the second frequency, wherein the uplinkportions, during which the FDD UEs transmit the uplink information, aredistinct from the downlink portions, during which the TDD UEs receivethe downlink information, of the TDD frame periods.
 9. The apparatus ofclaim 8, wherein the operations further comprise: prior to transmissionof the downlink information on the second frequency channel, reconfigurethe frequency channel on which the FDD UEs are configured to transmitthe uplink information as the second frequency channel.
 10. Theapparatus of claim 8, wherein the operations further comprise:dynamically modify at least one of a time interval of the TDD frameperiods, a time interval of the downlink portions of the TDD frameperiods, or a time interval of the uplink portions of the TDD frameperiods.
 11. The apparatus of claim 8, wherein the wireless networkincludes a long term evolution (LTE) wireless network.
 12. The apparatusof claim 8, wherein the wireless network includes a cellular network.13. The apparatus of claim 8, wherein at least one of the FDD UEsincludes a headset.
 14. The apparatus of claim 8, wherein at least oneof the FDD UEs includes a mobile phone.
 15. A non-transitorycomputer-readable medium having instructions stored thereon, which inresponse to execution by a processor, cause the processor to perform orcontrol performance of operations that include: transmit downlinkinformation on a first frequency channel to one or more frequency domainduplex (FDD) user equipments (UEs); reconfigure a second frequencychannel, on which the FDD UEs are configured to transmit uplinkinformation, to transmit downlink information to one or more time domainduplex (TDD) UEs; transmit the downlink information on the secondfrequency channel during downlink portions of TDD frame periods of thesecond frequency channel to the one or more TDD UEs; and control uplinktransmissions, to transmit the uplink information on the secondfrequency channel, from the FDD UEs to occur during uplink portions ofthe TDD frame periods of the second frequency channel, wherein theuplink portions, during which the FDD UEs transmit the uplinkinformation, are distinct from the downlink portions, during which theTDD UEs receive the downlink information, of the TDD frame periods. 16.The non-transitory computer-readable medium of claim 15, wherein theoperations further comprise: dynamically modify at least one of a timeinterval of the TDD frame periods, a time interval of the downlinkportions of the TDD frame periods, or a time interval of the uplinkportions of the TDD frame periods.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the wireless networkincludes a long term evolution (LTE) wireless network.
 18. Thenon-transitory computer-readable medium of claim 15, wherein thewireless network includes a cellular network.
 19. The non-transitorycomputer-readable medium of claim 15, wherein at least one of the FDDUEs includes a headset.
 20. The non-transitory computer-readable mediumof claim 15, wherein at least one of the FDD UEs includes a mobilephone.